eDocs Home > BEA AquaLogic Data Services Platform Documentation > Data Services Developer's Guide > Contents

ALDSP: Roles and Responsibilities

The following summarizes typical roles and responsibilities related to creating and maintaining data services. 

Physical Data Service Development. Any team member can quickly create a set of physical data services from enterprise data sources.

Entity Data Service Development. A data architect with knowledge of the relationships between enterprise data sources can then create data services based on physical and previously developed logical data services.

Query Development. Once data services are created, an IT team member can create reusable query functions using the graphical XQuery Editor. The editor is directly tied to a Source View that facilitates code-based modifications to automatically-generated designs.

Deployment. Once data services are developed, they can be deployed from the IDE or by an administrator through the ALDSP Administration Console.

Application Development. Application designers can use data service query functions in their BEA WebLogic applications. Through Service Data Objects (SDO) and the Mediator API or an ALDSP Workshop Control, applications can retrieve and update data, yet remaining insulated from the complexities of managing the underlying data interaction.

Metadata Management. Administrators, architects, and designers can use the Service Explorer for real-time introspection of disparate data source metadata that has been developed through AquaLogic Data Services Platform.